{ }
001122334455554433221100
001122334455554433221100

RBS Rescue: A £45 Billion Bailout and Its Aftermath

NatWest's tumultuous journey post-bailout saw leadership changes and significant financial losses, culminating in a near-£10 billion loss for taxpayers. Despite efforts to re-privatize and refocus on the UK market, public anger and operational challenges persisted, leading to the eventual ousting of CEO Alison Rose in 2023. The government’s gradual sell-down of shares began in 2015, but the long-term impact of the financial crisis remains evident.

natwest chair thanks taxpayers as bank prepares for private ownership return

NatWest's chair, Rick Haythornthwaite, expressed gratitude to UK taxpayers for the £46bn bailout during the 2008 financial crisis, emphasizing the bank's transformation into a safer, customer-focused institution. As it prepares for a return to private ownership, he assured shareholders that there are no plans for risky expansions despite government pressure for growth. Shareholders overwhelmingly approved a new executive pay policy, raising the CEO's potential earnings while maintaining a cautious approach to risk.

Machinary offers a groundbreaking, modular, and customizable solution that provides advanced financial news and statistical analysis. Our platform goes beyond traditional quantitative analysis, offering users a comprehensive understanding of real-time market dynamics, event detection, and risk analysis.

Address

Newsletter

© 2025 by Machinary.com - Version: 1.0.0.0. All rights reserved

Layout

Color mode

Theme mode

Layout settings

Seems like the connection with the server has been lost. It can be due to poor or broken network. Please hang on while we're trying to reconnect...
Oh snap! Failed to reconnect with the server. This is typically caused by a longer network outage, or if the server has been taken down. You can try to reconnect, but if that does not work, you need to reload the page.
Oh man! The server rejected the attempt to reconnect. The only option now is to reload the page, but be prepared that it won't work, since this is typically caused by a failure on the server.